﻿
<!DOCTYPE html>
<html>
<head>
   <title>Toolbars and Panels &gt; Font Properties &gt; Masters</title>
   <meta name="viewport" content="width=device-width, initial-scale=1">
   <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />   
   <meta http-equiv="X-UA-Compatible" content="IE=edge" />
   <meta name="generator" content="Help &amp; Manual" />
   <meta name="keywords" content="Ascent,CapHeight,Descent,Left Side Bearing,Metrics,Right Side Bearing,Typo Ascender,Typo Descender,Win Ascent,Win Descent,x-Height" />
   <meta name="description" content="A non-variable font requires one master, while variable fonts need multiple masters as needed for interpolation to work within the variation space." />
   <link type="text/css" href="default.css" rel="stylesheet" />
   <link type="text/css" href="custom.css" rel="stylesheet" />

   <style TYPE="text/css" media="screen"> 
      html, body { margin:0; 
        padding:0; 
        background: #ffffff; 
      } 
      div#printheader { display: none; }
      #idheader { 
        width:100%; 
        height:auto; 
        padding: 0; 
        margin: 0;
        position: fixed;
        top: 0;
        z-index: 2;
      } 
      /* The "min-height" for "#idheader table" ensures that the (blue) header of the topic
         has at least the same height as the header of the navigation panel left of it */
      #idheader table { background: #2C5D88; min-height: 59px }             
      #idheader h1 span { color: #FFF }     
      #idnav {
        text-align: right;
        width: 126px;
        vertical-align: middle;        
      } 
      #idnav a { text-decoration: none }
      #idnav span {
        display: inline-block;
        width: 24px;
        height: 24px;
        margin-left: 4px;
        background:url('hm_webhelp_buttons_grey.png') top left no-repeat;
      } 
      #idnav a span {
        background-image:url('hm_webhelp_buttons_white.png');
      } 
      #idnav a span:hover {
        background-image:url('hm_webhelp_buttons_orange.png');
      } 
      #idnav span.hmbtnprev { background-position: 0 -32px }
      #idnav span.hmbtnnext { background-position: -24px -32px }
      #idnav span.hmbtntop  { background-position: -48px -32px }
      #idnav span.hmbtntoggle  { width: 20px; background-position: -70px -32px }
      #idnav span.hmbtnprint  { background-position: -88px -32px }

      #callout-table, #overview-table {display:block; position:relative; top:0; left:0;}
      #callout-icon {display:block; position:absolute; top:-11px; left:-11px;}
      #callout-icon-flag {display:block; position:absolute; top:-11px; left:-8px;}
      #callout-table a {text-decoration: none; color: blue;}
      #callout-table a:visited {text-decoration: none; color: blue;}
      #overview-table a {text-decoration: none; color: black;}
      #overview-table a:visited {text-decoration: none; color: black;}
      #callout-table a:hover, #overview-table a:hover {text-decoration: underline;}       
      p.help-url { margin: 20px 0 5px 0; text-align: center; font-size: 80%; text-decoration: none }      
      #switchtoggles { text-align: right; padding: 0 2px 0 0; font-size: 90%; } 
      .sync-toc { color: #FFF; font-size: 8pt; font-weight: bold; display: none; }
      .sync-toc a { color: #FFF; text-decoration: none; font-weight: bold;}
      .sync-toc a:visited { color: #FFF; }
      .sync-toc a:hover { text-decoration: underline; }
      a.hmanchor { display: inline-block; margin-top: -4em; padding-top: 4em }	  
   </style>
   <style TYPE="text/css" media="print">
      div#idheader, img.dropdown-toggle-icon, p.help-url { display:none } 
   </style>
   <script type="text/javascript" src="jquery.js"></script>
   <script type="text/javascript" src="helpman_settings.js"></script>
   <script type="text/javascript" src="helpman_topicinit.js"></script>
   <script type="text/javascript" src="hmpopup_html.js"></script>

   <script type="text/javascript">
     HMSyncTOC("index.html", "fontproperties-masters.html");
   </script>
   <script type="text/javascript" src="highlight.js"></script>
   <script type="text/javascript">
     $(document).ready(function(){highlight();});
   </script>
</head>
<body>


<div id="printheader"><h1 class="p_Heading1" style="page-break-after: avoid;"><span class="f_Heading1">Panels - Font Properties - Masters</span></h1>
</div>
<div id="idheader">
<div id="idheaderbg">
<table style="width:100%;border:none;margin:0px;" cellspacing="0" cellpadding="0"> 
  <tr>
    <td class="topichead" style="text-align:left; vertical-align:bottom">
      <p class="sync-toc">&lt;&lt; <a rel="nofollow" href="index.html?fontproperties-masters.html" target="_top">Click to Display Table of Contents</a> &gt;&gt;</p>
      <p class="crumbs"><b>Navigation:</b>&nbsp;
      
      Toolbars and Panels &gt; Font Properties&nbsp;&gt;</p>
   
      <h1 class="p_Heading1" style="page-break-after: avoid;"><span class="f_Heading1">Panels - Font Properties - Masters</span></h1>

    </td>
    <td class="topichead" id="idnav">
      
      <a href="fontproperties-axes.html" title="Previous Topic"><span class="hmbtnprev"></span></a>
      <a href="welcometothefontcreator.html" title="Parent Chapter"><span class="hmbtntop"></span></a>
      <a href="fontproperties-instances.html" title="Next Topic"><span class="hmbtnnext"></span></a>
      
    </td>
  </tr>  
</table>
</div>
</div>  

<div id="idcontent"><div id="innerdiv">
<!-- Ask Internet Explorer 6.users to update their obsolete and dangerous browser --> 
<!--[if lt IE 7]><div style=' clear: both; height: 59px; padding:0 0 0 15px; position: relative;'><a href="http://windows.microsoft.com/en-US/internet-explorer/products/ie/home?ocid=ie6_countdown_bannercode"><img src="http://storage.ie6countdown.com/assets/100/images/banners/warning_bar_0000_us.jpg" border="0" height="42" width="820" alt="You are using an outdated browser. For a faster, safer browsing experience, upgrade for free today." /></a></div><![endif]-->

<!--ZOOMRESTART-->
<p class="p_Normal">A non-variable font requires one master, while variable fonts need multiple masters as needed for interpolation to work within the variation space.</p>
<h2 class="p_Heading2" style="page-break-after: avoid;"><span class="f_Heading2">Masters</span></h2>
<h2 class="p_Heading2" style="page-break-after: avoid;"><img width="604" height="564" style="margin:0;width:604px;height:564px;border:none" src="fontcreator_161_fontproperties_masters.png"/></h2>
<p class="p_Normal">For a variable font, be sure to include masters with axis locations that allow interpolation. It is common to add masters at the extremes (minimum and maximum axis coordinates), but this is not always necessary. Just remember, a variable font encompasses a whole design space, which is consist of regions which are always rectilinear. A font with two axes, weight and width, can work just fine with these masters:</p>
<div style="text-align: left; text-indent: 0; padding: 0 0 0 0; margin: 0 0 10px 0;"><table style="border:none; border-spacing:0;">
<tr>
<td style="vertical-align:top; padding:0; border:none"><p class="p_Normal">Master</p>
</td>
<td style="vertical-align:top; padding:0; border:none"><p class="p_Normal">Weight</p>
</td>
<td style="vertical-align:top; padding:0; border:none"><p class="p_Normal">Width</p>
</td>
<td style="vertical-align:top; padding:0; border:none"><br />
</td>
</tr>
<tr>
<td style="vertical-align:top; padding:0; border:none"><p class="p_Normal">Light</p>
</td>
<td style="vertical-align:top; padding:0; border:none"><p class="p_Normal">300</p>
</td>
<td style="vertical-align:top; padding:0; border:none"><p class="p_Normal">100</p>
</td>
<td style="vertical-align:top; padding:0; border:none"><br />
</td>
</tr>
<tr>
<td style="vertical-align:top; padding:0; border:none"><p class="p_Normal">Regular (default)</p>
</td>
<td style="vertical-align:top; padding:0; border:none"><p class="p_Normal">400</p>
</td>
<td style="vertical-align:top; padding:0; border:none"><p class="p_Normal">100</p>
</td>
<td style="vertical-align:top; padding:0; border:none"><br />
</td>
</tr>
<tr>
<td style="vertical-align:top; padding:0; border:none"><p class="p_Normal">Bold</p>
</td>
<td style="vertical-align:top; padding:0; border:none"><p class="p_Normal">700</p>
</td>
<td style="vertical-align:top; padding:0; border:none"><p class="p_Normal">100</p>
</td>
<td style="vertical-align:top; padding:0; border:none"><br />
</td>
</tr>
<tr>
<td style="vertical-align:top; padding:0; border:none"><p class="p_Normal">Condensed</p>
</td>
<td style="vertical-align:top; padding:0; border:none"><p class="p_Normal">400</p>
</td>
<td style="vertical-align:top; padding:0; border:none"><p class="p_Normal">75</p>
</td>
<td style="vertical-align:top; padding:0; border:none"><br />
</td>
</tr>
<tr>
<td style="vertical-align:top; padding:0; border:none"><p class="p_Normal">Ultra-expanded</p>
</td>
<td style="vertical-align:top; padding:0; border:none"><p class="p_Normal">400</p>
</td>
<td style="vertical-align:top; padding:0; border:none"><p class="p_Normal">200</p>
</td>
<td style="vertical-align:top; padding:0; border:none"><br />
</td>
</tr>
</table>
</div>
<p class="p_Normal">So, it might not be needed to include corner masters, like Bold Ultra-condensed (Weight 700, Width 200). And if you later discover there is a need for it, you can add such master later in the design process.</p>
<p class="p_Normal">Some glyph outlines need additional layers, e.g. outlines with curves that have inflection points (a change in direction of curvature), like “S”. Then add an additional master and only add layers for these outlines. No need to add layers for all glyphs, if they already interpolate the way you want.</p>
<p class="p_NormalHead" style="page-break-after: avoid;"><span class="f_NormalHead">Name</span></p>
<p class="p_Normal">The name of the masters is only used while designing the font. It is not part of the exported font. Therefor localisation is not supported here.</p>
<h2 class="p_Heading2" style="page-break-after: avoid;"><span class="f_Heading2">Axis Location</span></h2>
<p class="p_Normal">Each master has a particular position within the variation space of a variable font. The dimensions of the whole space is defined by the axes. The axis location values are <span style="font-weight: bold;">design scale coordinates</span>. The user scale coordinates may be different if an axis has mappings.</p>
<h2 class="p_Heading2" style="page-break-after: avoid;"><span class="f_Heading2">Metrics for Horizontal Writing Mode</span></h2>
<p class="p_NormalHead" style="page-break-after: avoid;"><img width="604" height="792" style="margin:0;width:604px;height:792px;border:none" src="fontcreator_162_fontproperties_masters2.png"/></p>
<p class="p_NormalHead" style="page-break-after: avoid;"><span class="f_NormalHead">Typo Ascender</span></p>
<p class="p_Normal">The typographic ascender for this font. Remember that this is not the same as the <span style="font-weight: bold;">Ascender</span> value in the <span style="font-weight: bold;">Metrics</span> tab, which Apple defines in a far different manner.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">The suggested usage for <span style="font-weight: bold;">Typo Ascender</span> is that it be used in conjunction with <span style="font-weight: bold;">units per em</span> to compute a typographically correct default line spacing. The goal is to free applications from Macintosh or Windows-specific metrics which are constrained by backward compatibility requirements. These new metrics, when combined with the character design widths, will allow applications to lay out documents in a typographically correct and portable fashion. </p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">For CJK (Chinese, Japanese, and Korean) fonts that are intended to be used for vertical writing (in addition to horizontal writing), the required value for <span style="font-weight: bold;">Typo Ascender</span> is that which describes the top of the design space (also known as em-square). For example, if the design space of the font extends from coordinates 0,-120 to 1000,880 (that is, a 1000x1000 box set 120 design units below the Latin <a href="javascript:void(0);" onclick="return hmshowPopup(event, popid_1780635977, this);" class="popuplink">baseline</a>), then the value of <span style="font-weight: bold;">Typo Ascender</span> must be set to 880. Failing to adhere to these requirements will result in incorrect vertical layout. </p>
<p class="p_NormalHead" style="page-break-after: avoid;"><span class="f_NormalHead">Typo Descender</span></p>
<p class="p_Normal">The typographic <a href="javascript:void(0);" onclick="return hmshowPopup(event, popid_1518352117X, this);" class="popuplink">descender</a> for this font. Remember that this is not the same as the <span style="font-weight: bold;">Descender</span> value in the <span style="font-weight: bold;">Metrics</span> tab, which Apple defines in a far different manner.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">The suggested usage for <span style="font-weight: bold;">Typo Descender</span> is that it be used in conjunction with units per em to compute a typographically correct default line spacing. The goal is to free applications from Macintosh or Windows-specific metrics, which are constrained by backward compatibility requirements. These new metrics, when combined with the character design widths, will allow applications to lay out documents in a typographically correct and portable fashion.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">For CJK (Chinese, Japanese, and Korean) fonts that are intended to be used for vertical writing (in addition to horizontal writing), the required value for <span style="font-weight: bold;">Typo Descender</span> is that which describes the bottom of the design space (aka, em-square). For example, if the design space of the font extends from coordinates 0,-120 to 1000,880 (that is, a 1000x1000 box set 120 design units below the Latin <a href="javascript:void(0);" onclick="return hmshowPopup(event, popid_1780635977, this);" class="popuplink">baseline</a>), then the value of <span style="font-weight: bold;">Typo Descender</span> must be set to -120. Failing to adhere to these requirements will result in incorrect vertical layout.  &nbsp; &nbsp; &nbsp; &nbsp;</p>
<p class="p_NormalHead" style="page-break-after: avoid;"><span class="f_NormalHead">Typo Line Gap</span></p>
<p class="p_Normal">The typographic line gap for this font. Remember that this is not the same as the <span style="font-weight: bold;">Line Gap</span> value, which Apple defines in a far different manner.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">The suggested usage for <span style="font-weight: bold;">Typo Line Gap</span> is that it be used in conjunction with <span style="font-weight: bold;">units per em</span> to compute a typographically correct default line spacing. Typical values average 7-10% of units per em.</p>
<p class="p_NormalHead" style="page-break-after: avoid;"><span class="f_NormalHead">Win Ascent</span></p>
<p class="p_Normal">The <a href="ascent.html" class="topiclink">ascender</a> metric for Windows. This, too, is distinct from Apple’s Ascender value and from the <span style="font-weight: bold;">Typo Ascender</span> value. <span style="font-weight: bold;">Win Ascent</span> is computed as the yMax for all characters in the Windows ANSI character set. Win Ascent is used to compute the Windows font height and default line spacing. For <span style="font-weight: bold;">Symbol fonts</span>, it is the same as yMax.</p>
<p class="p_NormalHead" style="page-break-after: avoid;"><span class="f_NormalHead">Win Descent</span></p>
<p class="p_Normal">The <a href="javascript:void(0);" onclick="return hmshowPopup(event, popid_1518352117X, this);" class="popuplink">descender</a> metric for Windows. This, too, is distinct from Apple’s Descender value and from the <span style="font-weight: bold;">Typo Descender</span> value. <span style="font-weight: bold;">Win Descent</span> is computed as the -yMin for all characters in the Windows ANSI character set. <span style="font-weight: bold;">Win Descent</span> is used to compute the Windows font height and default line spacing. For <span style="font-weight: bold;">Symbol fonts</span>, it is the same as -yMin.</p>
<p class="p_NormalHead" style="page-break-after: avoid;"><span class="f_NormalHead">Ascender (Macintosh-specific)</span></p>
<p class="p_Normal">Typographic <a href="ascent.html" class="topiclink">ascent</a></p>
<p class="p_NormalHead" style="page-break-after: avoid;"><span class="f_NormalHead">Descender (Macintosh-specific)</span></p>
<p class="p_Normal">Typographic descent</p>
<p class="p_NormalHead" style="page-break-after: avoid;"><span class="f_NormalHead">Line Gap (Macintosh-specific)</span></p>
<p class="p_Normal">Typographic line gap. Negative Line Gap values are treated as zero.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_NoteorTip"><span class="f_NoteorTip">Tip: To automatically calculate ascender and descender values press the Calculate button. It will try to preserve original line spacing, so it might also affect line gap.</span></p>
<p class="p_NormalHead" style="page-break-after: avoid;"><span class="f_NormalHead">x-Height</span></p>
<p class="p_Normal">This metric specifies the distance between the <a href="javascript:void(0);" onclick="return hmshowPopup(event, popid_1780635977, this);" class="popuplink">baseline</a> and the approximate height of non-ascending lowercase letters measured in Funits. This value would normally be specified by a type designer but in situations where that is not possible, for example when a legacy font is being converted, the value may be set equal to the top of the unscaled and unhinted glyph bounding box of the glyph encoded at U+0078 (LATIN SMALL LETTER X). If no glyph is encoded in this position the field should be set to 0. </p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">This metric, if specified, can be used in font substitution: the xHeight value of one font can be scaled to approximate the apparent size of another. </p>
<p class="p_NormalHead" style="page-break-after: avoid;"><span class="f_NormalHead">CapHeight</span></p>
<p class="p_Normal">This metric specifies the distance between the <a href="javascript:void(0);" onclick="return hmshowPopup(event, popid_1780635977, this);" class="popuplink">baseline</a> and the approximate height of uppercase letters measured in Funits. This value would normally be specified by a type designer but in situations where that is not possible, for example when a legacy font is being converted, the value may be set equal to the top of the unscaled and unhinted glyph bounding box of the glyph encoded at U+0048 (LATIN CAPITAL LETTER H). If no glyph is encoded in this position the field should be set to 0.</p>
<p class="p_Normal">&nbsp;</p>
<p class="p_Normal">This metric, if specified, can be used in systems that specify type size by capital height measured in millimeters. It can also be used as an alignment metric; the top of a drop capital, for instance, can be aligned to the CapHeight metric of the first line of text.</p>
<p class="p_NormalHead" style="page-break-after: avoid;"><span class="f_NormalHead">Italic Angle (degrees)</span></p>
<p class="p_Normal">Italic angle in degrees from the vertical. Zero for upright text, positive for text that leans to the right (forward).</p>
<p class="p_NoteorTip"><span class="f_NoteorTip">Tip: you can type “x / y” (run/rise) for italic angle and caret slope. Be sure to press Enter to let FontCreator know you intend to set the value as run/rise.</span></p>
<p class="p_Normal" style="page-break-inside: avoid;"><span class="f_NormalHead">Caret Slope (degrees)</span></p>
<p class="p_Normal">The slope of the caret in degrees from the vertical. The caret is the mark used to indicate where something is to be inserted into a text. It is usually represented by a blinking vertical bar, but with italic (or slanted) fonts it can have an angle.</p>
<p class="p_Normal" style="page-break-inside: avoid;"><span class="f_NormalHead">Caret Offset</span></p>
<p class="p_Normal">The amount by which a slanted highlight on a glyph needs to be shifted to produce the best appearance. Set to 0 for non-slanted fonts. FontCreator uses this value to offset the left side-bearing of glyphs.</p>
<p class="p_Normal"><span class="f_NormalHead">Use typo metrics for line spacing</span></p>
<p class="p_Normal">If set, it is strongly recommended to use <span style="font-weight: bold;">Typo Ascender - Typo Descender + Typo Line Gap</span> as a value for default line spacing for this font.</p>
<p class="p_NormalHead" style="page-break-after: avoid;"><span class="f_Heading2">Metrics for Vertical Writing Mode</span></p>
<p class="p_Normal"><img width="604" height="586" style="margin:0;width:604px;height:586px;border:none" src="fontcreator_163_fontproperties_masters3.png"/></p>
<p class="p_Normal">In general vertical metrics are only useful with fonts that are used for vertical writing. So we recommend to only include them in CJK (Chinese, Japanese, and Korean) fonts. If enabled, it is also useful to show top and bottom bearings. You can enable it within the <a href="metrics_options.html" class="topiclink">Metrics Options dialog</a>. Use <a href="autometrics-metrics.html" class="topiclink">Auto Metrics</a> to set vertical spacing of a range of glyphs.</p>
<p class="p_NormalHead" style="page-break-after: avoid;"><span class="f_NormalHead">Vertical Typo Ascender</span></p>
<p class="p_Normal">The distance from the ideographic em-box center baseline for the vertical axis to the right of the ideographic em-box and is usually set to 0.5*units_per_em.</p>
<p class="p_NormalHead" style="page-break-after: avoid;"><span class="f_NormalHead">Vertical Typo Descender</span></p>
<p class="p_Normal">The distance from the ideographic em-box center baseline for the vertical axis to the left of the ideographic em-box and is usually set to -0.5*units_per_em.</p>
<p class="p_NormalHead" style="page-break-after: avoid;"><span class="f_NormalHead">Vertical Typo LineGap</span></p>
<p class="p_Normal">The vertical typographic gap. An application can determine the recommended line spacing for single spaced vertical text for an OpenType font by the following expression: ideographic em-box width + Vertical Typo LineGap.</p>
<p class="p_NormalHead" style="page-break-after: avoid;"><span class="f_NormalHead">Vertical Caret Slope</span></p>
<p class="p_Normal">The slope of the caret in degrees. Set value equal to 90 (a horizontal caret) for regular/nonslanted fonts.</p>
<p class="p_NormalHead" style="page-break-after: avoid;"><span class="f_NormalHead">Vertical Caret Offset</span></p>
<p class="p_Normal">The amount by which the highlight on a slanted glyph needs to be shifted away from the glyph to produce the best appearance. Set value equal to 0 for regular/nonslanted fonts.</p>
<p class="p_NormalHead" style="page-break-after: avoid;"><span class="f_Heading2">Additional Metrics</span></p>
<p class="p_Normal"><img width="604" height="768" style="margin:0;width:604px;height:768px;border:none" src="fontcreator_164_fontproperties_masters4.png"/></p>
<p class="p_NoteorTip"><span class="f_NoteorTip">Note: Word processors that support OpenType layout features may use the Subscript (subs) and Superscript (sups) features, if available in the font.</span></p>
<p class="p_NormalHead" style="page-break-after: avoid;"><span class="f_NormalHead">Subscript horizontal font size</span></p>
<p class="p_Normal">The recommended horizontal size in font design units for subscripts for this font. </p>
<p class="p_NormalHead" style="page-break-after: avoid;"><span class="f_NormalHead">Subscript vertical font size</span></p>
<p class="p_Normal">The recommended vertical size in font design units for subscripts for this font. </p>
<p class="p_NormalHead" style="page-break-after: avoid;"><span class="f_NormalHead">Subscript x offset</span></p>
<p class="p_Normal">The recommended horizontal offset in font design units for subscripts for this font.</p>
<p class="p_NormalHead" style="page-break-after: avoid;"><span class="f_NormalHead">Subscript y offset</span></p>
<p class="p_Normal">The recommended vertical offset in font design units from the <a href="javascript:void(0);" onclick="return hmshowPopup(event, popid_1780635977, this);" class="popuplink">baseline</a> for subscripts for this font.</p>
<p class="p_NormalHead" style="page-break-after: avoid;"><span class="f_NormalHead">Superscript horizontal font size</span></p>
<p class="p_Normal">The recommended horizontal size in font design units for superscripts for this font.</p>
<p class="p_NormalHead" style="page-break-after: avoid;"><span class="f_NormalHead">Superscript vertical font size</span></p>
<p class="p_Normal">The recommended vertical size in font design units for superscripts for this font.</p>
<p class="p_NormalHead" style="page-break-after: avoid;"><span class="f_NormalHead">Superscript x offset</span></p>
<p class="p_Normal">The recommended horizontal offset in font design units for superscripts for this font.</p>
<p class="p_NormalHead" style="page-break-after: avoid;"><span class="f_NormalHead">Superscript y offset</span></p>
<p class="p_Normal">The recommended vertical offset in font design units from the <a href="javascript:void(0);" onclick="return hmshowPopup(event, popid_1780635977, this);" class="popuplink">baseline</a> for superscripts for this font.</p>
<p class="p_NormalHead" style="page-break-after: avoid;"><span class="f_NormalHead">Strikeout position</span></p>
<p class="p_Normal">The position of the strikeout stroke relative to the <a href="javascript:void(0);" onclick="return hmshowPopup(event, popid_1780635977, this);" class="popuplink">baseline</a> in font design units, this positive values represent distances above the baseline. Aligning the strikeout position with the em dash is suggested. Note, however, that the strikeout position should not interfere with the recognition of standard characters, and therefore should not line up with crossbars in the font. For a Roman font with a 2048 em square, 460 is suggested.</p>
<p class="p_NormalHead" style="page-break-after: avoid;"><span class="f_NormalHead">Strikeout Thickness</span></p>
<p class="p_Normal">Width of the strikeout stroke in font design units. This field should normally be the width of the em dash, and should also match the underline thickness. For a Roman font with a 2048 em square, 102 is suggested.</p>
<p class="p_NormalHead" style="page-break-after: avoid;"><span class="f_NormalHead">Underline Position</span></p>
<p class="p_Normal">This is the suggested distance of the top of the underline from the <a href="javascript:void(0);" onclick="return hmshowPopup(event, popid_1780635977, this);" class="popuplink">baseline</a> (negative values indicate below baseline).</p>
<p class="p_NormalHead" style="page-break-after: avoid;"><span class="f_NormalHead">Underline Thickness</span></p>
<p class="p_Normal">Suggested value for the underline thickness. In general, the underline thickness should match the thickness of the underscore character ($5F), and should also match the strikeout thickness.</p>
<p class="p_NormalHead" style="page-break-after: avoid;"><span class="f_NormalHead">Calculate</span></p>
<p class="p_Normal">The calculate button calculates the values so that they look correct in Microsoft Word.</p>
<p class="p_NormalHead" style="page-break-after: avoid;"><span class="f_NoteorTip">Note: It is up to word-processing software to use these values. However, be aware that not all software uses these values uniformly, so when superscripts, subscripts, strikeout, and underline look correct in one application, they might look wrong in another application.</span></p>
<p class="p_Normal"><img width="604" height="796" style="margin:0;width:604px;height:796px;border:none" src="fontcreator_165_fontproperties_masters5.png"/></p>
<p class="p_NormalHead" style="page-break-after: avoid;"><span class="f_Heading2">Hinting</span></p>
<p class="p_Normal"><span style="font-size: 11pt;">This</span><span style="font-size: 11pt;"> describes the preferred rasterization techniques for the typeface </span>when it is rendered on grayscale-capable devices. It also has some use for monochrome devices, which may use the table to turn off hinting at very large or small sizes, to improve performance. It was invented for screen output and will not be used by printer drivers.</p>
<p class="p_NoteorTip"><span class="f_NoteorTip">Note: smoothing is optional and only works with TrueType based outlines, so it will not be included if you export fonts with CFF based outlines.</span></p>
<p class="p_NoteorTip">If there are no ranges defined in a typeface, the rasterizer may apply default rules to decide how to render the glyphs on grayscale devices. The rasterizer will use the ClearType related values, if ClearType is enabled.</p>
<p class="p_Normal">At very small sizes, the best appearance on grayscale devices can usually be achieved by rendering the glyphs in grayscale without gridfitting. At intermediate sizes, gridfitting (also known as hinting) and monochrome rendering will usually produce the best appearance. At large sizes, the combination of gridfitting and grayscale rendering will typically produce the best appearance. Click the <span style="font-weight: bold;">Generate</span> button to get smoothing settings based on these recommendations.</p>
<p class="p_Normal">To add a new range, press the <span style="font-weight: bold;">Add</span> button. To remove a range, select it and press the <span style="font-weight: bold;">Delete</span> button.</p>
<p class="p_NormalHead" style="page-break-after: avoid;"><span class="f_Heading2">Note</span></p>
<p class="p_Normal">A note may be useful for you as font designer, but it is not part of the exported font.</p>
<p class="p_SeeAlso" style="page-break-after: avoid; border-right: none; border-bottom: none; border-left: none;"><span class="f_SeeAlso">See also:</span></p>
<p class="p_Normal"><a href="metrics_options.html" class="topiclink">Metrics Options</a></p>

<!--ZOOMSTOP-->
</div></div>
<script type="text/javascript">

  $(document).ready(function(){
    $(window).bind('resize', function() {
      var y = $('#idheader').height(); 
      $('#idcontent').css('margin-top', y);
      var par = window.parent;
      if ($( par ).width() <= $( window ).width()+20) {
        $('#idheader').css('position', 'relative');
        $('#idcontent').css('margin-top', 0);
        $('#idbacktotop').css('display', 'block');
        $('.hmanchor').css('margin-top', -20);
	$('.hmanchor').css('padding-top', 20);
      }
      else {
        $('#idheader').css('position', 'fixed');
        $('#idcontent').css('margin-top', $('#idheader').height());
        $('#idbacktotop').css('display', 'none');
        $('.hmanchor').css('margin-top', -y-20);
	$('.hmanchor').css('padding-top', y+20);
      }
    });
    
    $(window).resize(); //trigger event for initially small displays
  });

if ((!parent.hmNavigationFrame) && (parent.location) && (parent.location.href)) { $('.sync-toc').show();$('p.crumbs').hide();}

</script>
</body>
</html>
